Allocation of data radio bearers for quality of service flows

ABSTRACT

An example method can include receiving information identifying a quality of service (QoS) flow for a communication session involving a user equipment (UE). The information can include a QoS profile and a QoS flow identifier (QFI). The method can include identifying, from a QoS profile, a QoS configuration identifier associated with the QoS flow and selecting a data radio bearer (DRB) for the communications associated with the QoS flow. The DRB can be selected based on a mapping of a plurality of DRBs to a plurality of QoS flows, and the mapping can be based on corresponding QoS configuration identifiers of the plurality of QoS flows. The method can include assigning the QoS flow to the selected DRB by adding the QFI of the QoS flow to the mapping relative to the selected DRB and causing the communications associated with the QoS flow to be transmitted using the selected DRB.

BACKGROUND

5G/New Radio (5G/NR) is a next generation global wireless standard.5G/NR provides various enhancements to wireless communications, such asflexible bandwidth allocation, improved spectral efficiency,ultra-reliable low-latency communications (URLLC), beamforming,high-frequency communication (e.g., millimeter wave (mmWave)), and/orthe like.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1D are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems,functional architectures, and/or methods described herein can beimplemented.

FIG. 3 is a diagram of an example functional architecture of an examplecore network described herein.

FIG. 4 is a diagram of example components of one or more devices of FIG.2.

FIG. 5 is a flowchart of an example process associated with allocationof data radio bearers for quality of service flows.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

In a wireless telecommunications system (which can be referred to hereinas “the system”), a particular quality of service (QoS) can be providedfor a data flow. Such a data flow, that is to receive a particular QoScan be referred to as a QoS flow. A QoS flow can be identified by aparticular identifier, such as a QoS flow identifier (QFI). A QFI for aQoS flow can be communicated, within QoS information, to one or moredevices (e.g., a user equipment (UE), a base station, a user planefunction (UPF) and/or the like) of the wireless telecommunicationssystem to indicate that communications associated with that QoS flow areto receive a QoS as described in the QoS information. In such cases, theQFI can be identified in a field of a communication that includes theQoS information. Furthermore, that field can have a limited number ofbits (e.g., six bits, seven bits, eight bits, and/or the like), asdefined by a standard. In some instances, the wirelesstelecommunications system maps QoS flows, at a one-to-one ratio, toresources (e.g., data radio bearers (DRBs)) of an access network. Insuch cases, the QFI of the QoS flows can be used within a mapping of theQoS flows to the resources. However, in the wireless telecommunicationssystem, there can be fewer resources that can be used than the number ofdifferent possible QFIs (or the number of different types of dataflows). For example, while there can be more than 250 possible QFIs,there might be only 20 or fewer resources to which the QoS flows can bemapped. Accordingly, in such cases, the number of different QoS flowscan be limited to the number of resources. For example, if the size ofthe QFI field allows for 256 different QFIs (or different QFI values),rather than a possible 256 different QFIs being available for mapping toresources, previous techniques are limited to, for example, 16 differentQoS flows if there are 16 resources, 29 different QoS flows if there are29 resources, and so on.

According to some implementations described herein, QoS flows can bemapped to resources of an access network using a plurality of differentQoS parameters, other than a QFI of the QoS flow. The QoS parameters canbe indicated in a QoS profile of the QoS information. Using theplurality of different parameters permits a more granular mapping of QoSflows to the resources of the access network, relative to previoustechniques, thus providing for a more efficient use of the resources anda wider variety of different possible types of QoS flows that can bemapped to the resources. As described herein, a wireless communicationsystem, such as a 5G wireless telecommunications network, can permit theQoS profile to include a QoS configuration identifier and/or one or moreQoS parameters that can be used to map QoS flows to resources of anaccess network. In this way, the QoS configuration identifier (e.g., a5G QoS identifier (5QI)) can permit QoS flows that have a same QoSconfiguration identifier to be mapped to a same resource.

Accordingly, some implementations described herein can permit a moreefficient mapping of QoS flows to resources, which can be referred toherein as DRBs, of an access network relative to previous techniques, byallowing for a greater variety of different types of QoS flows to becommunicated through the access network at a particular time. In thisway, computing resources associated with frequently replacing QoS flowmappings to add a new QoS flow to the mapping can be conserved.Furthermore, enabling more types of QoS flows to be mapped to an accessnetwork at a given time reduces the likelihood of droppingcommunications and enables more efficient use of radio resources. Forexample, communications involving QoS flows that are removed from themapping due to the limited number of possible mappings of QoS flows, areless likely to be dropped, thus conserving computing resources and/ornetwork resources associated with retransmitting data associated withthe dropped communications or errors caused by the droppedcommunications.

FIGS. 1A-1D are diagrams of one or more example implementations 100described herein. Example implementation(s) 100, in FIG. 1A, includes awireless communication system with a core network that includes a policyand control function (PCF), a session mobility function (SMF), and aUPF, a user equipment (UE), and an access network (shown as a radioaccess network (RAN)). As further shown in FIG. 1A, a plurality ofresources (DRBi through DRBM, wherein M>1) enable communication betweenthe UE and the RAN (or a base station of the RAN) and a communicationsession (e.g., a protocol data unit (PDU) session) is established, viaan N3 interface, between the RAN and the UPF of the core network. Asshown in the example mappings of FIGS. 1B-1D, one or more mappings ofQoS flows to the plurality of resources can be maintained using one ormore QoS parameters included within a QoS profile of a QoS flow.

As further shown in FIG. 1A, and by reference number 110, the UE ispermitted to communicate data (e.g., transmit data and/or receive data)associated with QoS flows according to QFIs and/or corresponding QoSrules. The QFIs and/or QoS rules can be provided to the UE by the SMF ofthe core network via an N1 interface based on the UE requesting tocommunicate according to one or more QoS corresponding to the QFIs. TheQFIs and/or QoS rules can be defined and/or enabled for the UE accordingto policies associated with the QoS flows and/or the UE (e.g., asmaintained by the PCF). For example, the SMF (e.g., along with an accessand mobility management function (AMF)) can perform one or moreverifications and/or authentication processes of the UE in associationwith the requested QoS. Accordingly, the QFIs and/or QoS rules providedby the SMF to the UE can correspond to the QoS that is to be providedfor QoS flows of the UE.

In this way, the UE can be authorized to transmit QoS flows through theRAN to transmit data via a PDU session associated with the core network.

As further shown in FIG. 1A, and by reference 120, the RAN receivesinformation identifying the QoS flows. The RAN can receive theinformation, via the N2 interface, from the SMF and/or an AMF of thecore network. In some implementations, the SMF can provide the QFIsand/or packet filter sets to the UPF to permit the UPF to applycorresponding QoS to the QoS flows of the PDU session.

As described herein, the information identifying the QoS flows caninclude a QFI and a QoS profile. Further, the QoS profile can includeone or more of a QoS configuration identifier (shown as an 8 bit “5QI”in FIG. 1A), an allocation and retention priority (ARP), and one or morebitrate parameters (shown as “BR parameters”), which can indicatewhether the QoS flow requires a guaranteed bit rate (GBR). In someimplementations, one or more preemption indicators (e.g., a preemptioncapability indication (PCI), a preemption vulnerability indication(PVI), and/or the like) associated with the ARP can be included withinthe QoS profile. In some implementations, for non-GBR QoS flows, thebitrate parameters can include a reflective QoS attribute (RQA). In someimplementations, for GBR QoS flows, the bitrate parameters can includeone or more of a guaranteed flow bit rate (GFBR) (e.g., for uplinkand/or for downlink), a maximum flow bitrate (MFBR) (e.g., for uplinkand/or for downlink), a notification control, a maximum packet loss rate(MPLR) (e.g., for uplink and/or for downlink), and/or the like.

In this way, the RAN can obtain QoS profiles associated with QoS flowsof communications involving the UE, to permit the UE to communicate withthe RAN using one or more resources that are to be allocated for the QoSflows according to the QoS profiles.

As further shown in FIG. 1A, and by reference number 130, the RAN mapsQoS flows to DRBs based on the QoS profiles. The RAN can include a QoSflow allocator that is configured to identify the QoS parameters of theQoS flow and map the QoS flows to DRBs of the RAN accordingly. In someimplementations, the QoS flow allocator can be a component of a basestation, a RAN scheduler, or another device of the RAN.

As described herein, the QoS flow allocator can maintain a mapping ofQoS flows to DRBs of the RAN. The mapping can be maintained by the QoSflow allocator to permit the RAN to select a data radio bearer (DRB) forthe communications associated with the QoS flow. For example, uponreceipt of information identifying the QoS flow (or QFI andcorresponding QoS profile), the QoS flow allocator can look up (e.g.,search for, refer to, and/or the like), in the mapping, one or more QoSparameters of the QoS profile to determine which DRB is allocated forthe one or more QoS parameters. Based on the mapping indicating that aDRB is allocated for the one or more QoS parameters, the QoS flowallocator can map the QoS flow to the DRB to assign the QoS flow to theDRB. In other words, the QoS flow allocator can assign the QoS flow tothe DRB by adding the QFI of the QoS flow to the mapping relative to theselected DRB for the QoS flow. In this way, when a communication,associated with the QoS flow, is to be transmitted or received by theRAN, the communication can be assigned to that DRB to cause the data ofQoS flow to be transmitted and/or received using that DRB.

As described herein, the QoS flow allocator can generate and/or maintainthe mapping according to one or more settings that indicate which QoSparameters of a QoS profile are to be used to map QoS flows to theresources of the RAN. For example, as described below in connection withFIGS. 1B-1D, the QoS flow allocator can map the QoS flows according toone or more different sets of QoS parameters of the QoS flows.

In this way, the RAN can configure a mapping of QoS flows to resourcesof the RAN based on QoS profiles of the QoS flows, to cause the UE tocommunicate with the RAN using resources defined by the mapping.

As further shown in FIG. 1A, and by reference number 140, communicationsbetween the UE and the RAN use the designated DRBs according to thecorresponding QoS flows of the communications. Accordingly, for acommunication involving a first QoS flow (shown as QoS flow 1), the UEcan be assigned, by the RAN, to use a first DRB (e.g., DRB₁).Furthermore, for a communication involving a second QoS flow (shown asQoS flow 2), the UE can be assigned, by the RAN, to use a second DRB(e.g., a DRB other than DRB₁, such as one of DRB₂ to DRB_(M)).

In some implementations, a plurality of UEs can be configured tocommunicate with the UE according to the mapping of QoS flows to theDRBs. Accordingly, several UEs, associated with sending and/or receivingQoS flows having a same QoS configuration identifier and/or one or moreother QoS parameters (e.g., QoS parameters that are the same or similarin that QoS parameters have a same or similar value (e.g., with athreshold range), have a same or similar setting (e.g., both enabled ordisabled), and/or the like), can use a same DRB to communicate with theRAN when the communication involves those QoS flows.

In this way, the core network and/or the RAN can be configured to permitone or more UEs to communicate via designated resources of the RANaccording to one or more QoS parameters of a QoS profile. Therefore, thecore network and/or the RAN can be configured to map a greater varietyof QoS flows to resources of the RAN to permit the one or more UEs toreceive a greater variety of QoS from a wireless communication system.

As shown in FIG. 1B, and by reference number 130 a, a mapping canprovide that each DRB of a plurality of DRBs can be allocated for QoSflows that have a same QoS configuration identifier (shown as “5QI”). Asshown in FIG. 1B, the mapping indicates that each DRB of the pluralityof DRBs can be allocated for QoS flows that have a single, same QoSconfiguration identifier. Accordingly, multiple QoS flows that have adifferent QFI can be mapped to a same DRB if the multiple QoS flows areassociated with and/or include a same QoS configuration identifier. Asdescribed herein, the QoS configuration identifier can be includedwithin the QoS profile provided by the SMF.

As described herein, the QoS configuration identifier can berepresentative of one or more characteristics of the QoS that is to beprovided for QoS flows associated with the QoS configuration identifier.Such characteristics can include one or more of: resource type (e.g.,GBR or non-GBR), priority level (e.g., which can be any suitable range,such as 0-100) scheduling, packet delay budget (PDB), packet error rate(PER), and/or the like. As described herein, the one or morecharacteristics can correspond to one or more QoS parameters that areincluded in the QoS profile of the information identifying the QoS. TheQoS configuration identifier can be configured for one or more types ofservices associated with the QoS flows. For example, a first QoSconfiguration identifier can be used to identify a QoS flow involvingconversational voice, a second QoS configuration identifier can be usedto identify real-time gaming and/or V2X messages, a third QoSconfiguration identifier can be used to one or more of voice service,live-streaming video, and/or interactive gaming, and so on. Astandardized mapping of QoS configuration identifiers to correspondingcharacteristics of the QoS for the QoS configuration identifier and/orexample services can be used by the UE, the RAN, and/or the core networkto identify the characteristics of a QoS for a particular QoSconfiguration identifier.

In the example mapping of FIG. 1B, a first set of QoS flows j, k, 1, x,y, z are associated with 5QI “4E,” a second set of QoS flows a, b, c, d,e are associated with 5QI “1F,” a third set of QoS flows f, g, h, i, sare associated with 5QI “3A,” and a fourth set of QoS flows m, n, o, p,q are associated with 5QI “89.” As further shown in the mapping, basedon the 5QIs of the above QoS flows, the first set of QoS flows can bemapped to DRB 0, the second set of QoS flows can be mapped to DRB 1, thethird set of QoS flows can be mapped to DRB 2, and the fourth set of QoSflows can be mapped to DRB 3.

As further shown by the mapping of FIG. 1B, the mapping can indicate aminimum ARP (e.g., a minimum ARP priority level) for QoS flows mapped toa corresponding DRB. For example, because one or more of the QoS flows,that are mapped to a particular DRB based on having the same 5QI, canhave different ARPs, the RAN can set an ARP for each of the DRBs thatcorresponds to a minimum ARP of the QoS flows that are assigned to thatDRB. In some implementations, for each DRB, the RAN can determine theminimum ARP based on analyzing (and/or comparing) the QoS profiles foreach of the corresponding QoS flows mapped to the DRB and comparing thecorresponding ARPs to identify the minimum ARP. As a specific example,assume that QoS flow j has the minimum ARP relative to the QoS flows ofthe first set of QoS flows. Accordingly, the RAN can set the ARP for thefirst set of QoS flows (and/or DRB 0) to be the ARP of QoS flow j (shownas “ARP”). In this way, the first set of QoS flows, which are mapped toDRB 0, can receive a QoS with an ARP that is different from an ARP thatis identified in respective QoS profiles of the first set of QoS flows.

As further shown by the mapping of FIG. 1B, the mapping can indicatewhether preemption capability and/or preemption vulnerability for QoSflows of the respective DRBs are to be enabled and/or disabled. Forexample, because one or more of the QoS flows, that are mapped to aparticular DRB based on the 5QI, can have different settings forpreemption capability and/or preemption vulnerability, the RAN canenable preemption capability and/or preemption vulnerability for each ofthe DRBs based on whether any of the QoS flows that are mapped to aparticular DRB are to have preemption capability and/or preemptionvulnerability enabled. In some implementations, for each DRB, the RANcan determine whether preemption capability and/or preemptionvulnerability is to be enabled based on analyzing the QoS profiles foreach of the corresponding QoS flows mapped the DRB. As a specificexample, assume that one or more QoS flows of the first set of QoS flowshas preemption vulnerability enabled, but none of the QoS flows of thefirst set of QoS flows has preemption capability enabled. Accordingly,preemption vulnerability can be enabled for the QoS flows mapped to DRB0 (as shown by the “0”), and preemption capability is not to be enabledfor the QoS flows mapped to DRB 0 (as shown by the “1”). As anotherspecific example, assume that one or more of the QoS flows of the secondset of QoS flows has preemption capability enabled, but none of the QoSflows of the second set of QoS flows has preemption vulnerabilityenabled. Accordingly, preemption capability can be enabled for QoS flowsmapped to DRB 1 (as shown by the “0”) and preemption vulnerability isnot to be enabled for the QoS flows mapped to DRB 1 (as shown by the“1”). In this way, if a PCI of a QoS profile for a QoS flow indicatesthat preemption capability is to be enabled for the QoS flow, themapping allows for the RAN to cause the DRB to provide a QoS thatprovides preemption capability (e.g., by enabling the preemptioncapability for that DRB). Furthermore, if a PVI of a QoS profile for aQoS flow indicates that preemption vulnerability is to be enabled forthe QoS flow, the mapping allows for the RAN to cause the DRB to providea QoS that provides preemption vulnerability (e.g., by enabling thepreemption vulnerability for that DRB).

As further shown by the mapping of FIG. 1B, the mapping can indicate aGFBR and/or a MFBR for QoS flows of the respective DRBs. For example,because one or more of the QoS flows, that are mapped to a particularDRB based on having the same 5QI, can have different GFBRs and/ordifferent MFBRs, the RAN can set GFBR and/or MFBR for each of the DRBsthat corresponds to a sum of the GFBRs and/or a sum of the MFBRs of theQoS flows that are assigned to that DRB. In some implementations, foreach DRB, the RAN can determine the GFBR sum and/or the MFBR sum basedon analyzing (and/or comparing) the QoS profiles for each of thecorresponding QoS flows mapped to the DRB and summing the correspondingGFBRs and/or MFBRs to identify the GFBR sum and/or MFBR sum. As aspecific example, assume that QoS flows x, y, z have a GFBR and QoSflows k, 1 have an MFBR. Accordingly, the RAN can set the GFBR for thefirst set of QoS flows (and/or DRB 0) to be the sum of GFBRs of QoSflows x, y, z and the MFBR for the first set of QoS flows (and/or DRB 0)to be the MFBR of QoS flows k, 1. In this way, the first set of QoSflows, which are mapped to DRB 0, can receive a QoS with GFBR and/orMFBR that is different from a GFBR that is identified in respective QoSprofiles of the first set of QoS flows. As another example, assume thatnone of the QoS flows of the second set of QoS flows have a GFBR and/oran MFBR set. Accordingly, as shown, a GFBR and/or MFBR is not set forDRB 1.

As further shown by the mapping of FIG. 1B, the mapping can indicate aminimum MPLR for QoS flows mapped to corresponding DRBs. For example,because one or more of the QoS flows, that are mapped to a particularDRB based on having the same 5QI, can have different MPLRs, the RAN canset an MPLR for each of the DRBs that corresponds to a minimum MPLR ofthe QoS flows that are assigned to that DRB. In some implementations,for each DRB, the RAN can determine the minimum MPLR based on analyzing(and/or comparing) the QoS profiles for each of the corresponding QoSflows mapped to the DRB and comparing the corresponding MPLRs toidentify the minimum MPLR. As a specific example, assume that QoS flow fhas the minimum MPLR relative to the QoS flows of the third set of QoSflows. Accordingly, the RAN can set the MPLR for the first set of QoSflows to be the MPLR of QoS flow f (shown as “MPLRf”). In this way, thethird set of QoS flows, which are mapped to DRB 2, can receive a QoSwith an MPLR that is different from an MPLR that is identified inrespective QoS profiles of the third set of QoS flows.

In some implementations, the mapping can map QoS flows that have a same5QI and one or more of the other parameters of the QoS profile (e.g.,ARP, GFBR, MFBR, MPLR, and/or the like). For example, QoS flows with afirst 5QI and a first ARP can be mapped to a first DRB and QoS flowswith the first 5QI and a second ARP (that is different from the firstARP) can be mapped to a second DRB (that is different from the firstDRB). Although example implementations are described above in connectionwith determining an ARP, a PCI, a PVI, a GFBR/MFBR, and/or an MPLR, oneor more other techniques or implementations can be used.

In this way, the example mapping of FIG. 1B can permit a RAN to map QoSflows based on QoS configuration identifiers associated with the QoSflows. While mapping the QoS flows according to the QoS configurationidentifier can limit a number of different QoS configuration identifiersfor QoS flows (e.g., to the number of resources, if mapped in aone-to-one manner), using the QoS configuration identifier can permitmore QoS flows to be mapped, relative to using the QFI, becausedifferent QFIs can be associated with a same QoS configurationidentifier. Furthermore, the example mapping of FIG. 1B provides arelatively simple analysis and/or process for mapping QoS flows thatwould conserve resources (e.g., computing resources, such as processingresources and/or memory resources) associated with analyzing the QoSprofiles to map the QoS flows based on a plurality of other QoSparameters.

In FIG. 1C, as shown by reference number 130 b, a mapping can providethat a first set of DRBs are to be used to allocate QoS flows in a firstparticular manner and a second set of DRBs that are to be used toallocate QoS flows in a second particular manner. As shown in FIG. 1C,the RAN can use 16 DRBs (DRB 0 through DRB 15), although, in someimplementations, the RAN may be able to use more or fewer DRBs. In theexample of FIG. 1C, the first 13 DRBs (DRB 0 through DRB 12) can map QoSflows according to one or more of the examples described above inconnection with FIG. 1B. For example, once the first 13 DRBs are mappedaccording to SQIs of received QoS profiles, the RAN can begin mappingQoS flows based on one or more other types of QoS parameters of the QoSprofiles. For example, any subsequently received QoS flows that haveSQIs that are different from the SQIs of QoS flows mapped to DRBs 0-12,can be mapped to one or more of the remaining DRBs 13-15 based on one ormore other QoS parameters of the QoS profile for those QoS flows.

In the example mapping of FIG. 1C, the RAN can map QoS flows that have a5QI that is different from the SQIs of the QoS flows mapped to DRBs 0-12(which can be referred to in this example as an “unmapped 5QI”) based onwhether the QoS profile indicates that the QoS flow is configured with aGBR, whether the QoS flow has a priority level, and whether the QoS flowhas a delay critical GBR. Therefore, for each QoS flow that is receivedwith an unmapped 5QI, the RAN can inspect the QoS profile to identifyany GBR, any priority level, and/or any delay critical GBR to map theQoS flow to a DRB accordingly. A priority level can include a rangeand/or a set of ranges of the range (e.g., high, medium, low, and/or thelike).

In the example mapping of FIG. 1C, a fifth set of QoS flows xy, zt, tbcan be mapped to DRB 13, a sixth set of QoS flows cc, dc, ed can bemapped to DRB 14, and a seventh set of QoS flows ac, dy can be mapped toDRB 15. As described above, each of the fifth set of QoS flows can havea different QoS configuration identifier from one another, each of thesixth set of QoS flows can have a different QoS configuration identifierfrom one another, and each of the seventh set of QoS flows can have adifferent QoS configuration identifier from one another.

As shown in FIG. 1C, the fifth set of QoS flows are to have a GBR, adelay critical GBR, and a high (H) priority (e.g., greater than athreshold priority level). Further, the QoS flows of the sixth set ofQoS flows do not involve a GBR or delay critical GBR and have a low (L)priority level (e.g., less than a threshold priority level). The QoSflows of the seventh set of QoS flows are to have a GBR, might not havea delay critical GBR, and have a high priority level. Accordingly, forany QoS flow with an unmapped QoS configuration identifier, the RAN canmap those QoS flows to DRBs 13-15 according to the QoS parameters of theQoS flows of DRBs 13-15.

Furthermore, because QoS flows of DRBs 13-15 can be associated withdifferent QoS configuration identifiers, the RAN can set a minimum PDBand/or a minimum PER for each of DRBs 13-15 that corresponds to aminimum PDB and/or a minimum PER of the respective QoS flows that arecorrespondingly mapped to each of DRBs 13-15. For example, for each ofDRBs 13-15, the RAN can determine whether any of the QoS configurationidentifiers of each of DRBs 13-15 are associated with a PDB, and/or aPER (e.g., by referring to a standardized mapping of QoS configurationidentifiers to PDB and/or PER for the QoS configuration identifiers, asdescribed above). In such a case, if any of the QoS flows have a PDBand/or PER, the RAN can be configured to select the minimum PDB and/orminimum PER associated with the respective QoS flows that arecorrespondingly mapped to each of DRBs 13-15. As a specific example,assume the QoS configuration identifier for QoS flow xy has a PDB and aPER and that the PDB and the PER for QoS flow xy is the minimum of theQoS flows of the fifth set of QoS flows. Accordingly, the RAN can setthe PDB and/or the PER for the fifth set of QoS flows (and/or DRB 13) tobe the PDB for QoS flow xy and the PER for QoS flow xy, respectively.

In this way, for one or more DRBs (shown as DRBs for unmapped 5QIs), theRAN can map QoS flows according to one or more other QoS parametersother than the QoS configuration identifier of the QoS flows.Accordingly, the QoS flows can be mapped to a DRB regardless the QoSconfiguration identifier for a QoS flow. Accordingly, the mapping ofFIG. 1C can permit a relatively simplistic mapping for a first set ofDRBs (which can conserve computing resources associated with analyzingQoS parameters of the QoS profiles to map the QoS flows) withoutlimiting the different number of QoS flows to the number of resources ofthe RAN by using a second set of DRBs that can be mapped regardless ofthe QoS configuration. In this way, the second set of DRBs does notlimit the number of different QoS configuration identifiers for QoSflows to the number of resources of the RAN, thus allowing for greatervariety of QoS flows and efficient use of DRBs 0-15.

As shown in FIG. 1D, and by reference number 130 c, a mapping canprovide that each DRB of the plurality of DRBs of the RAN can beallocated for QoS flows based on one or more QoS parameters of the QoSflows. As shown in FIG. 1D, the mapping indicates that each DRB of theplurality of DRBs can be allocated for QoS flows that have the same orsimilar QoS parameters. In the example mapping of FIG. 1D, the exampleset of QoS parameters used to map QoS flows to DRBs include ARP,resource type (e.g., associated with GBR, non-GBR, MFBR, delay criticalGBR (shown as DC GBR), and/or the like), priority, PDB, and PER.Additionally, or alternatively, the mapping can map QoS flows to DRBsbased on a GBR parameter (e.g., the value of the GBR), a default maximumdata burst volume, a default averaging window, an RQA (for non-GBR), aPCI, a PVI, and/or the like. According to the mapping of FIG. 1D, theRAN can analyze and/or consider any or all QoS parameters of QoS flows.

To generate the mapping of FIG. 1D, the RAN can analyze the QoSparameters of QoS flows that are received in the QoS profile and/orrepresented by the QoS configuration identifier. The RAN can compare theQoS parameters to the groups of QoS parameters in the mapping todetermine which DRB is to be mapped to the QoS flow, and, thus, whichDRB is to be used for communications involving the QoS flow. Todetermine the similarity between the QoS parameters of a QoS flow andone or more sets of QoS parameters of the mapping, the RAN can apply oneor more scores to the QoS parameters based on the similarities betweencorresponding QoS parameters and/or based on discrete ranges ofcorresponding QoS parameters. In some implementations, when applying thescores to the QoS parameters, the RAN can apply a weight to the QoSparameters according to one or more preferences and/or settings.Accordingly, the RAN can determine, for each received QoS flow and basedon any number of QoS parameters of the QoS flow, which DRB is to bemapped to the QoS flow, and thus which DRB is to be used forcommunication involving the QoS flow.

In this way, the RAN can map QoS flows to DRBs based on one or more QoSparameters of the QoS flow. Accordingly, the RAN can allow for mappingof QoS flows to DRBs without being limited by the number of DRBs of theRAN. Therefore, a greater number of different QoS flows that provide agreater variety of QoS can be mapped to DRBs, thus allowing forefficient use of the DRBs and/or a greater number of services relativeto other techniques.

Accordingly, as described herein in connection with exampleimplementation(s) 100, the RAN can use a mapping of QoS flows to DRBsusing a QoS configuration identifier and/or one or more other QoSparameters. In this way, a greater variety of QoS and/or correspondingservices, can be offered by a wireless communication system, thusallowing for more efficient use of resources (e.g., DRBs), relative toprevious techniques, by enabling a more granular allocation of resourcesthe wireless communication system. Such granularity prevents wastingresources on communications and/or QoS flows that do not require one ormore QoS parameters of a QoS that must be assigned to thosecommunications and/or QoS flows because of the limited number ofdifferent QoS flows offered by the previous techniques.

As indicated above, FIGS. 1A-1D are provided as examples. Other examplescan differ from what is described with regard to FIGS. 1A-1D.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, can be implemented. As shown in FIG.2, environment 200 can include a UE 210, a RAN 220, a base station 222,a core network 230, and/or a data network 240. Devices of environment200 can interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

UE 210 can include one or more devices capable of communicating withbase station 222 and/or a network (e.g., RAN 220, core network 230, datanetwork 240, and/or the like). For example, UE 210 can include awireless communication device, a radiotelephone, a personalcommunications system (PCS) terminal (e.g., that can combine a cellularradiotelephone with data processing and data communicationscapabilities), a smart phone, a laptop computer, a tablet computer,and/or a similar device. UE 210 can be capable of communicating usinguplink (e.g., UE to base station) communications, downlink (e.g., basestation to UE) communications, and/or sidelink (e.g., UE-to-UE)communications. In some implementations, UE 210 can include amachine-type communication (MTC) UE, such as an evolved or enhanced MTC(eMTC) UE. In some implementations, UE 210 can include an Internet ofThings (IoT) UE, such as a narrowband IoT (NB-IoT) UE and/or the like.UE 210 can correspond to the UE of example implementation 100.

RAN 220 can include a base station and be operatively connected, via awired and/or wireless connection, to the core network 230. RAN 220 canfacilitate communication sessions between UEs and data network 240 bycommunicating application-specific data between RAN 220 and core network230. Data network 240 can include various types of data networks, suchas the Internet, a third-party services network, an operator servicesnetwork, a private network, a wide area network, and/or the like. RAN220 can correspond to the RAN of example implementation 100.

Base station 222 includes one or more devices capable of communicatingwith UE 210 using a cellular radio access technology (RAT). For example,base station 222 can include a base transceiver station, a radio basestation, a node B, an evolved node B (eNB), a gNB, a base stationsubsystem, a cellular site, a cellular tower (e.g., a cell phone tower,a mobile phone tower, etc.), an access point, a transmit receive point(TRP), a radio access node, a macrocell base station, a microcell basestation, a picocell base station, a femtocell base station, or a similartype of device. Base station 222 can transfer traffic between UE 210(e.g., using a cellular RAT), other base stations 222 (e.g., using awireless interface or a backhaul interface, such as a wired backhaulinterface), and/or data network 240. Base station 222 can provide one ormore cells that cover geographic areas. Some base stations 222 can bemobile base stations. Some base stations 222 can be capable ofcommunicating using multiple RATs.

In some implementations, base station 222 can perform scheduling and/orresource management for UEs 210 covered by base station 222 (e.g., UEs210 covered by a cell provided by base station 222). In someimplementations, base stations 222 can be controlled or coordinated by anetwork controller, which can perform load balancing, network-levelconfiguration, and/or the like. The network controller can communicatewith base stations 222 via a wireless or wireline backhaul. In someimplementations, base station 222 can include a network controller, aself-organizing network (SON) module or component, or a similar moduleor component. In other words, a base station 222 can perform networkcontrol, scheduling, and/or network management functions (e.g., forother base stations 222 and/or for uplink, downlink, and/or sidelinkcommunications of UEs 210 covered by the base station 222). In someimplementations, base station 222 can include a central unit andmultiple distributed units. The central unit can coordinate accesscontrol and communication with regard to the multiple distributed units.The multiple distributed units can provide UEs 210 and/or other basestations 222 with access to data network 240. Base station 222 can be abase station of the RAN of example implementation 100 and/or can becapable of performing one or more of the processes (e.g., mapping QoSflows to DRBs) described above in connection with example implementation100.

Core network 230 can include various types of core networkarchitectures, such as a 5G next generation (NG) Core (e.g., a corenetwork of FIG. 3), a Long-Term Evolution (LTE) Evolved Packet Core(EPC), and/or the like. In some implementations, core network 230 can beimplemented on physical devices, such as a gateway, a mobilitymanagement entity, and/or the like. In some implementations, thehardware and/or software implementing core network 230 can bevirtualized (e.g., through use of network function virtualization and/orsoftware-defined networking), thereby allowing for the use of composableinfrastructure when implementing core network 230. In this way,networking, storage, and compute resources can be allocated to implementthe functions of core network 230 in a flexible manner as opposed torelying on dedicated hardware and software to implement these functions.Core network 230 can correspond to the core network of exampleimplementation 100.

Data network 240 includes one or more wired and/or wireless datanetworks. For example, data network 240 can include an IP MultimediaSubsystem (IMS), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a private network such as a corporate intranet, an ad hocnetwork, the Internet, a fiber optic-based network, a cloud computingnetwork, a third party services network, an operator services network,and/or the like, and/or a combination of these or other types ofnetworks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as one or more examples. In practice, there can be additionaldevices and/or networks, fewer devices and/or networks, differentdevices and/or networks, or differently arranged devices and/or networksthan those shown in FIG. 2. Furthermore, two or more devices shown inFIG. 2 can be implemented within a single device, or a single deviceshown in FIG. 2 can be implemented as multiple, distributed devices.Additionally, or alternatively, a set of devices (e.g., one or moredevices) of environment 200 can perform one or more functions describedas being performed by another set of devices of environment 200.

FIG. 3 is a diagram of an example functional architecture of a corenetwork 300 in which systems and/or methods, described herein, can beimplemented. For example, FIG. 3 can show an example functionalarchitecture of a 5G NG core network included in a 5G wirelesstelecommunications system. In some implementations, the examplefunctional architecture can be implemented by a core network (e.g., corenetwork 230 of FIG. 2) and/or one or more of devices (e.g., a devicedescribed with respect to FIG. 4). While the example functionalarchitecture of core network 300 shown in FIG. 3 can be an example of aservice-based architecture, in some implementations, core network 300can be implemented as a reference-point architecture.

As shown in FIG. 3, core network 300 can include a number of functionalelements. The functional elements can include, for example, a networkslice selection function (NSSF) 302, a network exposure function (NEF)304, an authentication server function (AUSF) 306, a unified datamanagement (UDM) component 308, a PCF 310, an application function (AF)312, an AMF 314, a SMF 316, and a UPF 318. These functional elements canbe communicatively connected via a message bus 320, which can becomprised of one or more physical communication channels and/or one ormore virtual communication channels. Each of the functional elementsshown in FIG. 3 is implemented on one or more devices associated with awireless telecommunications system. In some implementations, one or moreof the functional elements can be implemented on physical devices, suchas an access point, a base station, a gateway, a server, and/or thelike. In some implementations, one or more of the functional elementscan be implemented on one or more computing devices of a cloud computingenvironment associated with the wireless telecommunications system. Insome implementations, the core network 300 can be operatively connectedto a RAN 220, a data network 240, and/or the like, via wired and/orwireless connections with UPF 318.

NSSF 302 can select network slice instances for UE's, where NSSF 302 candetermine a set of network slice policies to be applied at the RAN 220.By providing network slicing, NSSF 302 allows an operator to deploymultiple substantially independent end-to-end networks potentially withthe same infrastructure. In some implementations, each slice can becustomized for different services. NEF 304 can support the exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services and/or utilize network resources efficiently.

AUSF 306 can act as an authentication server and support the process ofauthenticating UEs in the wireless telecommunications system. UDM 308can store subscriber data and profiles in the wirelesstelecommunications system. UDM 308 can be used for fixed access, mobileaccess, and/or the like, in core network 300. PCF 310 can provide apolicy framework that incorporates network slicing, roaming, packetprocessing, mobility management, and/or the like.

AF 312 can determine whether UEs provide preferences for a set ofnetwork slice policies and support application influence on trafficrouting, access to NEF 304, policy control, and/or the like. AMF 314 canprovide registration and mobility management of UEs.

SMF 316 can support the establishment, modification, and release ofcommunications sessions in the wireless telecommunications system. Forexample, SMF 316 can configure traffic steering policies at UPF 318,enforce UE IP address allocation and policies, and/or the like. AMF 314and SMF 316 can act as a termination point for non-access stratum (NAS)signaling, mobility management, and/or the like. SMF 316 can act as atermination point for session management related to NAS. RAN 220 cansend information (e.g. the information that identifies the UE) to AMF314 and/or SMF 316 via PCF 310. As described herein, SMF 316 cancommunicate information identifying a QoS flow to UE 210, RAN 220, UPF318/, and/or the like.

UPF 318 can serve as an anchor point for intra/inter radio accesstechnology (RAT) mobility. UPF 318 can apply rules to packets, such asrules pertaining to packet routing, traffic reporting, handling userplane QoS, and/or the like. UPF 318 can determine an attribute ofapplication-specific data that is communicated in a communicationssession. UPF 318 can receive information (e.g., the information thatidentifies the communications attribute of the application) from RAN 220via SMF 316 or an application programming interface (API). Message bus320 represents a communication structure for communication among thefunctional elements. In other words, message bus 320 can permitcommunication between two or more functional elements. Message bus 320can be a message bus, a hypertext transfer protocol 2 (HTTP/2) proxyserver, and/or the like.

RAN 220 can include a base station and be operatively connected, via awired and/or wireless connection, to the core network 300 through UPF318. RAN 220 can facilitate communications sessions between UEs and datanetwork 240 by communicating application-specific data between RAN 220and core network 300. Data network 240 can include various types of datanetworks, such as the Internet, a third-party services network, anoperator services network, a private network, a wide area network,and/or the like.

The number and arrangement of functional elements shown in FIG. 3 areprovided as an example. In practice, there can be additional functionalelements, fewer functional elements, different functional elements, ordifferently arranged functional elements than those shown in FIG. 3.Furthermore, two or more functional elements shown in FIG. 3 can beimplemented within a single device, or a single functional element shownin FIG. 3 can be implemented as multiple, distributed devices.Additionally, or alternatively, a set of functional elements (e.g., oneor more functional elements) of core network 300 can perform one or morefunctions described as being performed by another set of functionalelements of core network 300.

FIG. 4 is a diagram of example components of a device 400. Device 400can correspond UE 210, base station 222, NSSF 302, NEF 304, AUSF 306,UDM 308, PCF 310, AF 312, AMF 314, SMF 316, UPF 318, and/or message bus320. In some implementations, UE 210, base station 222, NSSF 302, NEF304, AUSF 306, UDM 308, PCF 310, AF 312, AMF 314, SMF 316, UPF 318,and/or message bus 320 can include one or more devices 400 and/or one ormore components of device 400. As shown in FIG. 4, device 400 caninclude a bus 410, a processor 420, a memory 430, a storage component440, an input component 450, an output component 460, and acommunication interface 470.

Bus 410 includes a component that permits communication among multiplecomponents of device 400. Processor 420 is implemented in hardware,firmware, and/or a combination of hardware and software. Processor 420is a central processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 420includes one or more processors capable of being programmed to perform afunction. Memory 430 includes a random-access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 420.

Storage component 440 stores information and/or software related to theoperation and use of device 400. For example, storage component 440 caninclude a hard disk (e.g., a magnetic disk, an optical disk, and/or amagneto-optic disk), a solid-state drive (SSD), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 450 includes a component that permits device 400 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 450 caninclude a component for determining location (e.g., a global positioningsystem (GPS) component) and/or a sensor (e.g., an accelerometer, agyroscope, an actuator, another type of positional or environmentalsensor, and/or the like). Output component 460 includes a component thatprovides output information from device 400 (via, e.g., a display, aspeaker, a haptic feedback component, an audio or visual indicator,and/or the like).

Communication interface 470 includes a transceiver-like component (e.g.,a transceiver, a separate receiver, a separate transmitter, and/or thelike) that enables device 400 to communicate with other devices, such asvia a wired connection, a wireless connection, or a combination of wiredand wireless connections. Communication interface 470 can permit device400 to receive information from another device and/or provideinformation to another device. For example, communication interface 470can include an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a wireless local area networkinterface, a cellular network interface, and/or the like.

Device 400 can perform one or more processes described herein. Device400 can perform these processes based on processor 420 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 430 and/or storage component 440. As used herein,the term “computer-readable medium” refers to a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 430 and/or storagecomponent 440 from another computer-readable medium or from anotherdevice via communication interface 470. When executed, softwareinstructions stored in memory 430 and/or storage component 440 can causeprocessor 420 to perform one or more processes described herein.Additionally, or alternatively, hardware circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 4 are provided asan example. In practice, device 400 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 4. Additionally, or alternatively, aset of components (e.g., one or more components) of device 400 canperform one or more functions described as being performed by anotherset of components of device 400.

FIG. 5 is a flowchart of an example process 500 associated withallocation of DRBs for quality of service flows. In someimplementations, one or more process blocks of FIG. 5 can be performedby a base station (e.g., base station 222) of a RAN (e.g., RAN 220). Insome implementations, one or more process blocks of FIG. 5 can beperformed by another device or a group of devices separate from orincluding the base station, such as such as one or more components of aRAN (e.g., RAN 220), one or more components or functions (e.g., NSSF302, NEF 304, AUSF 306, UDM 308, PCF 310, AF 312, AMF 314, SMF 316, UPF318) of a core network (e.g., core network 300), and/or the like.

As shown in FIG. 5, process 500 can include receiving informationidentifying a QoS flow for a communication session involving a UE,wherein the information includes a QoS profile and a QFI (block 510).For example, the base station (e.g., using a processor 420, a memory430, a storage component 440, an input component 450, and acommunication interface 470, and/or the like) can receive informationidentifying a QoS flow for a communication session involving a UE, asdescribed above. In some implementations, the information includes a QoSprofile and a QFI.

As further shown in FIG. 5, process 500 can include identifying, by thedevice and from the QoS profile, a QoS configuration identifierassociated with the QoS flow, wherein the QoS configuration identifieris associated with a QoS that is to be provided for communicationsassociated with the QoS flow (block 520). For example, the base station(e.g., using a processor 420, a memory 430, a storage component 440, aninput component 450, and a communication interface 470, and/or the like)can identify, by the device and from the QoS profile, a QoSconfiguration identifier associated with the QoS flow, as describedabove. In some implementations, the QoS configuration identifier isassociated with a QoS that is to be provided for communicationsassociated with the QoS flow.

As further shown in FIG. 5, process 500 can include selecting a DRB forthe communications associated with the QoS flow, wherein the DRB isselected based on a mapping of a plurality of DRBs to a plurality of QoSflows, wherein the mapping is based on corresponding QoS configurationidentifiers of the plurality of QoS flows, and wherein the plurality ofDRBs are DRBs of a RAN associated with the device (block 530). Forexample, the base station (e.g., using a processor 420, a memory 430, astorage component 440, an input component 450, and a communicationinterface 470, and/or the like) can select a DRB for the communicationsassociated with the QoS flow, as described above. In someimplementations, the DRB is selected based on a mapping of a pluralityof DRBs to a plurality of QoS flows. In some implementations, themapping is based on corresponding QoS configuration identifiers of theplurality of QoS flows. In some implementations, wherein the pluralityof DRBs are DRBs of a RAN associated with the device.

As further shown in FIG. 5, process 500 can include assigning the QoSflow to the selected DRB by adding the QFI of the QoS flow to themapping relative to the selected DRB (block 540). For example, the basestation (e.g., using a processor 420, a memory 430, a storage component440, an output component 460, and a communication interface 470, and/orthe like) can assign the QoS flow to the selected DRB by adding the QFIof the QoS flow to the mapping relative to the selected DRB, asdescribed above.

As further shown in FIG. 5, process 500 can include causing thecommunications associated with the QoS flow to be transmitted using theselected DRB (block 550). For example, the base station (e.g., using aprocessor 420, a memory 430, a storage component 440, an outputcomponent 460, and a communication interface 470, and/or the like) cancause the communications associated with the QoS flow to be transmittedusing the selected DRB, as described above.

Process 500 can include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the mapping provides that each DRB of theplurality of DRBs is to be allocated for QoS flows that have a same QoSconfiguration identifier. In some implementations, the mapping providesthat each DRB of the plurality of DRBs is to be allocated for QoS flowsthat have a single, same QoS configuration identifier. In someimplementations, the mapping provides a first set of DRBs of theplurality of DRBs and a second set of DRBs of the plurality of DRBs. Insome implementations, each DRB of the first set of DRBs is to beallocated to QoS flows that have a single, same QoS configurationidentifier. In some implementations, at least one DRB of the second setof DRBs is to be allocated to QoS flows that have different QoSconfiguration identifiers relative to QoS flows assigned to eachrespective DRB.

In some implementations, the QoS profile includes an allocation andretention priority (ARP) for the QoS flow. In some implementations, themapping provides that each DRB, of the plurality of DRBs, is to beconfigured to provide the QoS based on a minimum ARP. In someimplementations, the minimum ARP comprises an ARP, of a plurality ofARPs corresponding to the QoS flows that are assigned to the respectiveDRB, associated with a lowest priority level.

In some implementations, the QoS profile includes a PCI that indicateswhether preemption capability is enabled or disabled for the QoS flow.In some implementations, if the PCI indicates that preemption capabilityis enabled for the QoS flow, the mapping provides that the selected DRBis to provide a QoS that provides preemption capability. In someimplementations, the QoS profile includes a PVI that indicates whetherpreemption vulnerability is enabled or disabled for the QoS flow. Insome implementations, if the PVI indicates that preemption vulnerabilityis enabled for the QoS flow, the mapping provides that the selected DRBis to provide a QoS that provides preemption vulnerability.

In some implementations, the mapping of the plurality of DRBs to theplurality of QoS flows is based on at least one of a guaranteed bitrate(GBR) parameter, a priority level, a packet delay budget, a resourcetype, a priority level, a default maximum data burst volume, a defaultaveraging window, or a packet error rate.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 can be performed in parallel.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations can be made inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold can, depending on the context,refer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, etc., depending on the context.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods described herein can beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the phrase “only one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

1. A method, comprising: receiving, by a device, information identifyinga quality of service (QoS) flow for a communication session involving auser equipment (UE), wherein the information includes a QoS profile anda QoS flow identifier (QFI), wherein the QoS profile includes apreemption vulnerability indication (PVI) that indicates whetherpreemption vulnerability is enabled or disabled for the QoS flow,wherein, if the PVI indicates that preemption vulnerability is enabledfor the QoS flow, a mapping provides that a selected data radio bearer(DRB) is to provide a QoS that provides the preemption vulnerability;identifying, by the device and from the QoS profile, a QoS configurationidentifier associated with the QoS flow, wherein the QoS configurationidentifier is associated with a QoS that is to be provided forcommunications associated with the QoS flow; selecting, by the device,the DRB for the communications associated with the QoS flow, wherein theDRB is selected based on the mapping of a plurality of DRBs to aplurality of QoS flows, wherein the mapping is based on correspondingQoS configuration identifiers of the plurality of QoS flows, wherein themapping provides that each DRB of the plurality of DRBs is to beallocated for QoS flows that have a single, same QoS configurationidentifier, and wherein the plurality of DRBs are DRBs of a radio accessnetwork (RAN) associated with the device; assigning, by the device, theQoS flow to the selected DRB by adding the QFI of the QoS flow to themapping relative to the selected DRB; and causing, by the device, thecommunications associated with the QoS flow to be transmitted using theselected DRB.
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. The method ofclaim 1, wherein the QoS profile includes an allocation and retentionpriority (ARP) for the QoS flow, and wherein the mapping provides thateach DRB, of the plurality of DRBs, is to be configured to provide theQoS based on a minimum ARP, wherein the minimum ARP comprises an ARP, ofa plurality of ARPs corresponding to the QoS flows that are assigned tothe respective DRB, associated with a lowest priority level.
 6. Themethod of claim 1, wherein the QoS profile includes: a preemptioncapability indication (PCI) that indicates whether the preemptioncapability is enabled or disabled for the QoS flow, wherein, if the PCIindicates that the preemption capability is enabled for the QoS flow,the mapping provides that the selected DRB is to provide the QoS thatprovides the preemption capability.
 7. The method of claim 1, whereinthe mapping of the plurality of DRBs to the plurality of QoS flows isbased on at least one of: a guaranteed bitrate (GBR) parameter, apriority level, a packet delay budget, a resource type, a defaultmaximum data burst volume, a default averaging window, or a packet errorrate.
 8. A device for wireless communication, comprising: a memory; andone or more processors operatively coupled to the memory, the memory andthe one or more processors configured to: receive informationidentifying a quality of service (QoS) flow for a communication sessioninvolving a user equipment (UE), wherein the information includes a QoSprofile and a QoS flow identifier (QFI), wherein the QoS profileincludes a preemption vulnerability indication (PVI) that indicateswhether preemption vulnerability is enabled or disabled for the QoSflow,  wherein, if the PVI indicates that preemption vulnerability isenabled for the QoS flow, a mapping of a plurality of DRBs to aplurality of QoS flows provides that a selected DRB is to provide a QoSthat provides the preemption vulnerability; identify, from the QoSprofile, a QoS configuration identifier associated with the QoS flow,wherein the QoS configuration identifier is associated with a QoS thatis to be provided for communications associated with the QoS flow;select a data radio bearer (DRB) for the communications associated withthe QoS flow, wherein the DRB is selected based on the mapping of theplurality of DRBs to the plurality of QoS flows, wherein the mapping isbased on correspond QoS configuration identifiers of the plurality ofQoS flows, wherein the mapping provides that each DRB of the pluralityof DRBs is to be allocated for QoS flows that have a single, same QoSconfiguration identifier, and wherein the plurality of DRBs are DRBs ofa radio access network (RAN) associated with the device; assign the QoSflow to the selected DRB by adding the QFI of the QoS flow to themapping relative to the selected DRB; and cause the communicationsassociated with the QoS flow to be transmitted using the selected DRB.9. (canceled)
 10. (canceled)
 11. (canceled)
 12. The device of claim 8,wherein the QoS profile includes an allocation and retention priority(ARP) for the QoS flow, and wherein the mapping provides that each DRB,of the plurality of DRBs, is to be configured to provide the QoS basedon a minimum ARP, wherein the minimum ARP comprises an ARP, of aplurality of ARPs correspond to the QoS flows that are assigned to therespective DRB, associated with a lowest priority level.
 13. The deviceof claim 8, wherein the QoS profile includes: a preemption capabilityindication (PCI) that indicates whether the preemption capability isenabled or disabled for the QoS flow, wherein, if the PCI indicates thatthe preemption capability is enabled for the QoS flow, the mappingprovides that the selected DRB is to provide the QoS that provides thepreemption capability.
 14. The device of claim 8, wherein the mapping ofthe plurality of DRBs to the plurality of QoS flows is based on at leastone of: a guaranteed bitrate (GBR) parameter, a priority level, a packetdelay budget, a resource type, a default maximum data burst volume, adefault averaging window, or a packet error rate.
 15. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors of a device, cause the one or more processors to: receiveinformation identifying a quality of service (QoS) flow for acommunication session involving a user equipment (UE), wherein theinformation includes a QoS profile and a QoS flow identifier (QFI),wherein the QoS profile includes a preemption vulnerability indication(PVI) that indicates whether preemption vulnerability is enabled ordisabled for the QoS flow,  wherein, if the PVI indicates thatpreemption vulnerability is enabled for the QoS flow, a mapping of aplurality of DRBs to a plurality of QoS flows provides that a selectedDRB is to provide a QoS that provides the preemption vulnerability;identify from the QoS profile, a QoS configuration identifier associatedwith the QoS flow, wherein the QoS configuration identifier isassociated with a QoS that is to be provided for communicationsassociated with the QoS flow; select a data radio bearer (DRB) for thecommunications associated with the QoS flow, wherein the DRB is selectedbased on the mapping of the plurality of DRBs to the plurality of QoSflows, wherein the mapping is based on correspond QoS configurationidentifiers of the plurality of QoS flows, wherein the mapping providesthat each DRB of the plurality of DRBs is to be allocated for QoS flowsthat have a single, same QoS configuration identifier, and wherein theplurality of DRBs are DRBs of a radio access network (RAN) associatedwith the device; assign the QoS flow to the selected DRB by adding theQFI of the QoS flow to the mapping relative to the selected DRB; andcause the communications associated with the QoS flow to be transmittedusing the selected DRB.
 16. (canceled)
 17. (canceled)
 18. (canceled) 19.The non-transitory computer-readable medium of claim 15, wherein the QoSprofile includes an allocation and retention priority (ARP) for the QoSflow, and wherein the mapping provides that each DRB, of the pluralityof DRBs, is to be configured to provide the QoS based on a minimum ARP,wherein the minimum ARP comprises an ARP, of a plurality of ARPscorrespond to the QoS flows that are assigned to the respective DRB,associated with a lowest priority level.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the QoS profile includes:a preemption capability indication (PCI) that indicates whetherpreemption capability is enabled or disabled for the QoS flow, wherein,if the PCI indicates that preemption capability is enabled for the QoSflow, the mapping provides that the selected DRB is to provide the QoSthat provides preemption capability.
 21. The method of claim 1, whereinthe configuration identifier is configured to identify a QoS flowinvolving conversational voice.
 22. The method of claim 1, wherein theconfiguration identifier is configured to identify real-time gamingand/or V2X messages.
 23. The method of claim 1, wherein theconfiguration identifier is configured to identify live-streaming videoand/or interactive gaming.
 24. The device of claim 8, wherein theconfiguration identifier is configured to identify a QoS flow involvingconversational voice.
 25. The device of claim 8, wherein theconfiguration identifier is configured to identify real-time gamingand/or V2X messages.
 26. The device of claim 8, wherein theconfiguration identifier is configured to identify live-streaming videoand/or interactive gaming.
 27. The non-transitory computer-readablemedium of claim 15, wherein the configuration identifier is configuredto identify a QoS flow involving conversational voice.
 28. Thenon-transitory computer-readable medium of claim 15, wherein theconfiguration identifier is configured to identify real-time gamingand/or V2X messages.
 29. The non-transitory computer-readable medium ofclaim 15, wherein the configuration identifier is configured to identifylive-streaming video and/or interactive gaming.